Artifact: Iteration Assessment
Purpose
Each iteration is concluded by an iteration assessment where the development organization makes a pause and reflects on what has happened, what was achieved or not, and why, and the lessons learned. Brief
Outline
(hyperlinks into HTML template in a new window) 1. Introduction1.1 Purpose1.2 Scope1.3 Definitions, Acronyms and Abbreviations1.4 References1.5 Overview2. Iteration Objectives Reached3. Adherence to Plan4. Use Cases and Scenarios Implemented5. Results Relative to Evaluation Criteria6. Test Results7. External Changes Occurred8. Rework RequiredTiming
Iteration assessments are created at the end of each iteration. They are not updated. Responsibility
The Worker: Project Manager is responsible for the iteration assessment. Tailoring
The Iteration Assessment is an essential artifact of the iterative approach. Depending on the scope and risk of the project and the nature of the iteration, it may range from a simple record of demonstration and outcomes to a complete formal test record. Iteration assessments are created at the end of each iteration. They are not updated. Additional Information
This assessment is a critical step in an iteration and should not be skipped. If iteration assessment is not done properly, many of the benefits of an iterative approach will be lost. Note that sometimes the right thing to do in this step is to revise the evaluation criteria rather than reworking the system. Sometimes the benefit of the iteration is in revealing that a particular requirement is not important, or too expensive to implement, or creates an unmaintainable architecture. In these cases, a cost/benefit analysis must be done and a business decision must be made. Metrics must be used as the basis of this assessment. |
Rational Unified
Process |